Open topic with navigation

Setting up repositories

Before you start recording, we recommend taking the time to set up the application in the repository. While these steps are optional, they can help you understand how QA Wizard Pro captures the windows, controls, and other properties in the application you are testing. Taking the time to set up the repository also guards against adding duplicate windows and controls to the repository.

Perform the following steps to add the application and prepare the repository data for testing.

1. Add the application and version to your local repository. See Adding applications.

2. Record a script for each major area of the application you are testing. Navigate to each window and dialog box that will be tested. If a window or dialog box is displayed during recording, QA Wizard Pro captures the window, controls, and properties of the window and controls. See Recording new scripts and Capturing window and control data.

3. Evaluate the window and control properties that are used to locate objects during playback. QA Wizard Pro automatically selects search criteria, but you may want to select different criteria based on your knowledge of the application. If duplicate windows and controls are added to the repository after recording or an object is not located during playback, it is a good indication you need to modify the search criteria. See Modifying window and control properties.

4. Review the window and control names in the repository. QA Wizard Pro tries to create meaningful names, but it may capture a generic name. The window and control names are referenced in scripts and used to locate objects. You may want to rename windows and controls to better match the application. See Renaming windows and controls. If you modify any names, you must also update scripts so QA Wizard Pro can successfully locate the objects using the new names. See Synchronizing with the application repository.

5. Run the scripts to make sure QA Wizard Pro can locate all windows and controls and the scripts work as expected. See Running scripts. If scripts fail, you may need to modify additional search criteria. See Modifying window and control properties.

6. Promote the application from the local repository to the global repository. See Promoting applications. If your organization does not use a global repository, you can export the application if you need share it with other testers. See Exporting applications.

7. If you promote the application to the global repository, rename or delete the corresponding application in the local repository. This ensures the correct repository is used when recording or running scripts. See Modifying application properties and Deleting applications.

You are now ready to record test scripts. If your organization uses a global repository, make sure you are using the application in the global repository instead of the local repository.

Note: For best results, record scripts or populate repositories to capture window and controls information whenever possible. If QA Wizard Pro cannot capture window or controls because they do not exist in the application or cannot be displayed when recording, you can manually add them to the repository to use when creating or modifying scripts. Only manually add windows or controls if you are familiar with how QA Wizard Pro uses properties and expected property values to locate controls during playback. See Configuring user-added windows and controls.